Repository navigation
docs: clarify that deprecation does not remove the latest flag - #1854
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A deprecated server version can remain
isLatest: true, which led clients in #1819 to interpret latest as active. Clarify that deprecation alone does not remove the flag and that clients must check lifecycle status separately. Explain that selecting an older active version requires inspecting version history and applying a client policy.Update the API reference, metadata guide, checked-in OpenAPI description, and runtime schema description consistently. Runtime selection behavior is unchanged.
Validation:
make validateandgit diff --checkpassed.